Example project — Frond is not real.

Authored demo content for a fictional plant-care app, rendered by the same parsers and held to the same invariants as a real project's dashboard. This is the system in use, three months in.

docs/planning/Open Questions & Assumptions Log.mdWorkingactive2026-07-20Read when: before each phase (your area's questions) — resolve or flag

Open Questions & Assumptions Log

Unresolved questions and working assumptions that affect upcoming work. Everything in this file is open — when a question resolves, it's deleted, so the count never lies.

1. The light premise

Can a phone camera separate light bands reliably enough to change a schedule?

Area: product · Opened: 2026-07-14 · Priority: high Thinking: This is the riskiest assumption in strategy/Scope & Constraints.md. If the camera cannot separate "bright indirect" from "medium" across different phone models, the room survey becomes a questionnaire and the product's premise weakens badly. The sweep is queued. Resolves when: the sensor accuracy sweep reports agreement against a real lux meter across at least four handsets.

Should a user be able to override a light band by hand?

Area: product · Opened: 2026-07-16 · Priority: medium Thinking: Overrides would rescue us where the camera is wrong, but they also let a user re-create the generic advice that kills plants. Leaning toward allowing it with the reasoning still visible, so the override is an informed one. Resolves when: decided in the Watering reminders walkthrough, or deferred with a trigger.

2. Retention

Does a streak motivate plant care, or does breaking one cause abandonment?

Area: product · Opened: 2026-07-20 · Priority: high Thinking: Care history is queued partly to build streaks, but a broken streak is exactly the moment our "copy never scolds" principle gets tested. A plant that died is not a lost badge. Worth designing the failure state before the success state. Resolves when: the Care history phase states its position, and copy is reviewed against the Vision principle.

3. Platform

Is the daily digest time a per-user setting or a per-household one?

Area: scope · Opened: 2026-07-19 · Priority: low Thinking: Trivial while there is one user per home, and it becomes a real question the moment shared households arrive. Recording it now so the schema choice is deliberate rather than accidental. Resolves when: shared households are scoped, or the notification schema is next touched.

How do we handle a user who moves house?

Area: product · Opened: 2026-07-08 · Priority: medium Thinking: Every room survey becomes invalid at once. Silently keeping old schedules is wrong; invalidating everything without warning is worse. Probably a prompt, but the trigger for detecting a move is unclear. Resolves when: a phase owns re-survey prompting, or it is promoted to a Future Consideration with a trigger.